Skip to main content

This is a new service – your feedback will help us to improve it.

Medway Council

Tree preservation zone

There is a problem

  • 93 entries must have dates in YYYY-MM-DD format

entity: 19128491

reference
M1-1998
name
tree-preservation-order
tree-preservation-zone-type
geometry
MULTIPOLYGON (((0.501016 51.388875,0.501023 51.388878,0.501026 51.388881,0.501027 51.388885,0.501024 51.388890,0.501013 51.388894,0.501007 51.388894,0.500999 51.388892,0.500995 51.388889,0.500993 51.388884,0.500995 51.388880,0.500999 51.388877,0.501004 51.388875,0.501016 51.388875)),((0.501111 51.388832,0.501118 51.388834,0.501122 51.388839,0.501121 51.388844,0.501118 51.388847,0.501106 51.388850,0.501100 51.388849,0.501093 51.388844,0.501092 51.388840,0.501096 51.388834,0.501103 51.388831,0.501111 51.388832)),((0.501082 51.388843,0.501092 51.388847,0.501094 51.388851,0.501094 51.388855,0.501090 51.388860,0.501082 51.388863,0.501073 51.388863,0.501065 51.388860,0.501062 51.388857,0.501061 51.388851,0.501065 51.388846,0.501073 51.388843,0.501082 51.388843)),((0.500979 51.388887,0.500990 51.388890,0.500993 51.388899,0.500990 51.388903,0.500980 51.388907,0.500971 51.388907,0.500962 51.388902,0.500960 51.388896,0.500965 51.388889,0.500970 51.388887,0.500979 51.388887)),((0.500951 51.388895,0.500955 51.388897,0.500957 51.388900,0.500956 51.388906,0.500952 51.388910,0.500938 51.388912,0.500929 51.388908,0.500927 51.388904,0.500927 51.388901,0.500930 51.388896,0.500937 51.388893,0.500946 51.388893,0.500951 51.388895)))
point
POINT (0.501022 51.388876)
notes
entry-date
2026-08-11
start-date

start-date must be a real date

1998-05-12
end-date

How to fix this issue

Your data is missing a start-date.

The Tree preservation zone guidance explains how to fix the issue:

start-date

The date that the tree preservation order came into force, written in YYYY-MM-DD format.

Example: 1984-03-28

How to improve Medway Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL